Skip to content

Bypass the softmax pytorch kernel that upscales to fp32#19865

Open
telgamal-1 wants to merge 1 commit into
pytorch:mainfrom
telgamal-1:export-D106729898
Open

Bypass the softmax pytorch kernel that upscales to fp32#19865
telgamal-1 wants to merge 1 commit into
pytorch:mainfrom
telgamal-1:export-D106729898

Conversation

@telgamal-1
Copy link
Copy Markdown
Contributor

Summary: Bypasses the PyTorch softmax kernel in static_attention that upscales activations to fp32, keeping the softmax computation in fp16. Also updates norm.py to handle the fp16 softmax output.

Differential Revision: D106729898

Summary: Bypasses the PyTorch softmax kernel in `static_attention` that upscales activations to fp32, keeping the softmax computation in fp16. Also updates `norm.py` to handle the fp16 softmax output.

Differential Revision: D106729898
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 29, 2026

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19865

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 1 Awaiting Approval, 2 Unrelated Failures, 6 Unclassified Failures

As of commit 4260f2a with merge base 42581f1 (image):

AWAITING APPROVAL - The following workflow needs approval before CI can run:

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 29, 2026
@linux-foundation-easycla
Copy link
Copy Markdown

CLA Not Signed

@meta-codesync
Copy link
Copy Markdown
Contributor

meta-codesync Bot commented May 29, 2026

@telgamal-1 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D106729898.

@github-actions
Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant